static link TA-LIB on Linux #628
Conversation
|
Stay tune for release 0.6.0 of TA-Lib. Multiple new downloadable assets will now include both shared and static libraries, and the autotools + cmake have been "modernized" for building from source on most platforms. |
|
@mrjbq7 For 0.6.0 there is a src.tar.gz specifically for "autotools source building". My question is: Would also a similar "CMake source building" asset be useful to this effort here? (Just trying to prioritize which TA-Lib packaging to work on. If we do not need a "CMake source" asset, then I will just keep working on generating various pre-compiled installation package, with more focus on Windows/MacOS). |
probably the autotools is sufficient? the one thing i need to work on is bundling the static library into the python module so that it doesn't require a compiler to install, or the previously installed TA-Lib C library. |
Ok, so I will keep working on static lib packaging (for various OS+arch). I made great progress recently with CPack for Github CI... trying hard to have the 0.6.0 release be our first one to have all its assets produced at the "push of a button". |
Static linking
TA-LIBmakesta-lib-pythona self-contained package that does not require TA-LIB to be installed on the target system. This makes it easier to deployta-lib-python.This patch adds several Makefile targets.
talib_statictarget downloads and compiles a static version of TA-LIB to the current directory, for use by other build targets._staticadded to existing build targets link to the static version of TA-LIB.To support building
ta-lib-pythonwith a static version ofTA-LIB, thesetup.pyscript has been updated to add a new variable namedlib_talib_static_lib. This variable is set to the file name of the static library if the environment variableTA_LINK_STATICis enabled. The corresponding settings are then made during build_extensions to link the static library.